Install go for python unit tests to use prism runner. - #36221
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
liferoad
approved these changes
Sep 20, 2025
Collaborator
Author
|
Thanks! |
17 tasks
Collaborator
Author
|
The PR significantly slows down Python Unit test. Revert it. |
shunping
added a commit
that referenced
this pull request
Sep 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR resolves an
[Errno 2] No such file or directory: 'go' errorin Python unit tests by installing Go, which is a prerequisite for the Prism runner.Previously, this issue was masked because the tests would silently fall back to the FnAPI runner. This change ensures that the Prism runner is used as intended when enabled as the default. This fixes the issue mentioned in #36219 (comment)